Searched hist:"5169 fb81" (Results 1 – 2 of 2) sorted by relevance
/freebsd/sys/dev/mlx5/mlx5_core/ |
H A D | mlx5_health.c | 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies
|
/freebsd/sys/dev/mlx5/ |
H A D | driver.h | 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies 5169fb81 Wed May 08 10:30:47 GMT 2019 Hans Petter Selasky <hselasky@FreeBSD.org> Protect from infinite sw-reset loop in mlx5core.
Avoid an infinite software firmware reset loop that may be caused by a hardware bug by limiting the maximum number of resets. The counter between resets is reset by request for reset, and not by a successful reset. The interval between two resets can be configured via sysctl: hw.mlx5.sw_reset_timeout which is global to all mlx5 devices in the system.
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies
|